home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20031118-20041115
/
000026_anthonypieper@cs.com_Mon Dec 1 11:35:05 2003.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Path: newsmaster.cc.columbia.edu!panix!news.maxwell.syr.edu!postnews1.google.com!not-for-mail
From: anthonypieper@cs.com (newexpectuser)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Problem in Kermit trying to get a file while sending it at the same time
Date: 1 Dec 2003 06:25:58 -0800
Organization: http://groups.google.com
Lines: 54
Message-ID: <f0bb0f39.0312010625.7751d0a7@posting.google.com>
References: <f0bb0f39.0311250532.1b93aad@posting.google.com> <slrnbs6r9i.oig.fdc@sesame.cc.columbia.edu> <f0bb0f39.0311260731.11d9eb29@posting.google.com> <f0bb0f39.0311261025.6fd175b5@posting.google.com> <slrnbsa0at.dm1.fdc@sesame.cc.columbia.edu>
NNTP-Posting-Host: 209.251.39.194
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1070288758 2185 127.0.0.1 (1 Dec 2003 14:25:58 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 1 Dec 2003 14:25:58 +0000 (UTC)
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:14702
I think I understand the following in the article:
"Notice that failure leaves the partial file (if any) in the working
directory, where the central-site watcher process does not look for
it. Thus transient failures do no harm. The script can be run again
later.
The /DELETE switch on the PUT command removes the source file after,
and only if, it was uploaded successfully; this prevents it from being
uploaded again (you could also have it moved or renamed). This way,
even if the script is run again for the same file, it will fail
immediately because the file is no longer there. Or, if a file of the
same name is in the same place, it is a new file that should be
uploaded.
Now we can move the uploaded file from the server's working directory
to its ready directory (the syntax assumes a UNIX-like file system on
server):
ftp rename \m(nameonly) ../ready/\m(nameonly)"
This solves my problem if I have a partial file, it will be transfered
into a directory (working) where my central-site server won't be
looking for it. Once this file has been dropped off 100%, then the
next time around I run to send files, I will then pickup a full file
in my working directory.
What I don't understand is with the above "ftp rename \m(nameonly)
../ready/\m(nameonly)", how does this avoid moving the partial file
from the working directory to the ready directory, there will still be
a file in the working directory albeit a partial file and this command
will move it along to the ready directory.
Frank da Cruz <fdc@columbia.edu> wrote in message news:<slrnbsa0at.dm1.fdc@sesame.cc.columbia.edu>...
> In article <f0bb0f39.0311261025.6fd175b5@posting.google.com>,
> newexpectuser wrote:
> : My main issue is the file(s) I want are on a secure ftp server. This
> : process has other companies dropping off their files off in a certain
> : directory, so if they are dropping off a large file in this directory
> : at the same time I am trying to get the files from this directory, it
> : seems I am getting only a partial file.
> :
> Please read the the FTP scripting tutorial, including the "transaction
> processing" section. I've referred you to it before. It addresses
> exactly this problem.
>
> http://www.columbia.edu/kermit/ftpscripts.html
>
> - Frank